A Software Tool for Requirements Specification - On Using the STORM Environment to Create SRS Documents
نویسندگان
چکیده
STORM, presented in this paper, is a UML-based software engineering tool designed for the purpose of automating as much of the requirements specification phase as possible. The main idea of the STORM approach is to combine adequate requirements writing with robust use case modelling in order to expedite the process leading up to the actual design of the software. This paper presents a description of our approach to software requirements specification as well as an overview of STORM’s design concepts, organizing principles, and modes of operation. Also included are examples of the tool’s use, a comparison between STORM and similar CASE tools, and a discussion of needed features for software environments that support text aspects of requirements and use case modelling.
منابع مشابه
Documenting Software Requirements Specification: A Revisit
Software Requirements Specification (SRS) is the key documentation, defining the functional and non-functional system requirements. By revisiting a number of in the literature much discussed key aspects related to SRS and extracting essential views from the author’s daily work experience, this papers stresses the importance of the SRS and examines the process, which enables the emergence of a q...
متن کاملTécnicas de Inspeção de Documentos de Requisitos de Software: um Estudo Comparativo
This paper presents an empirical study on inspection of Software Requirements Specification (SRS) Documents, aiming at evaluate the efficiency of reading techniques applied to these documents. The techniques of Checklist, Scenario, and Perspective were comparatively evaluated, through the inspection of the SRS of a software application, performed by software engineers. The definition and execut...
متن کاملReliable Mining of Automatically Generated Test Cases from Software Requirements Specification (SRS)
Writing requirements is a two-way process. In this paper we use to classify Functional Requirements (FR) and Non Functional Requirements (NFR) statements from Software Requirements Specification (SRS) documents. This is systematically transformed into state charts considering all relevant information. The current paper outlines how test cases can be automatically generated from these state char...
متن کاملResearch Findings on Empirical Evaluation of Requirements Specifications Approaches
Numerous software requirements specification (SRS) approaches have been proposed in software engineering. However, there has been little empirical evaluation of the use of these approaches in specific contexts. This paper describes the results of a mapping study, a key instrument of the evidence-based paradigm, in an effort to understand what aspects of SRS are evaluated, in which context, and ...
متن کاملUsing Linguistic Knowledge to Classify Non-functional Requirements in SRS documents
Non-functional Requirements (NFRs) such as software quality attributes, software design constraints and software interface requirements hold crucial information about the constraints on the software system under development and its behavior. NFRs are subjective in nature and have a broad impact on the system as a whole. Being distinct from Functional Requirements (FR), NFRs are dealt with speci...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2007